Even though Im able to resolve everything by name properly and IP. Its on the same physical network. In fact it prompts me for a username and password and then it gives me this error after the whell spins a minute. Reset the IP with netsh command. firewalls are all off. User is trying a repair now. We manually entered DNS servers. Tried wireless and wired connections. Can get to the web fine. Just wont join the domain. Does anyone have any ideas?

Hello, Please try proceeding like that: Choose a healthy DC / DNS server Make each DC you have points to this DC as primary DNS server Make each DC / DNS server points to its private IP address as secondary DNS server and 127.0.0.1 as third one Make sure that each DC you have has one IP address and one NIC card in use Make sure that needed ports for AD replication are not blocked: http://social.technet.microsoft.com/wiki/contents/articles/active-directory-replication-over-firewalls.aspx Use PortQry v2 for checking Make sure that DHCP client service is running Make sure that each DC has one IP address and one NIC card enabled Once done, run ipconfig /registerdns and restart netlogon on each DC you have. That should update the DNS records of all DCs you have on the chosen DC. This DC will then replicate your DNS zones to other DC / DNS servers in your domain. Another thing is that all DCs will start by the chosen DC for DNS resolution. Also, check that needed ports for AD authentication are not blocked: http://technet.microsoft.com/en-us/library/dd857231.aspx This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

If you don't have a DHCP server setup it issue proper IP/DNS settings, you probably will have to manually set your DNS suffix to reflect your domain. Either do that, or specify the FQDN of the domain and not the truncated "NT" style.